System event notification

ABSTRACT

The subject matter disclosed herein provides methods for distributing notifications to a user. The method can include receiving data encapsulating notifications from a device connected to a network that provide information relating to the device&#39;s status. The device can provide a health related treatment. The method can associate each notification with one or more notification categories relating to a function performed by the device or a location of the device. A table of users having one or more subscriptions to these notification categories can be accessed. The subscriptions can be automatically assigned to users based on the users&#39; role. A user can be identified from the table to distribute the one or more notifications to. The user can have a subscription that matches a notification category of the received notifications, and data comprising the notifications can be distributed to the user. Related apparatus, systems, techniques, and articles are also described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/679,690 filed Nov. 11, 2019 and now issued as U.S. Pat. No.10,986,059, which is a continuation of U.S. patent application Ser. No.13/916,472 filed Jun. 12, 2013 and now issued as U.S. Pat. No.10,476,921, the contents of which are herein incorporated by referencein their entirety.

TECHNICAL FIELD

The subject matter described herein relates to the distribution ofnotifications from various devices connected to a computing network in ahealthcare environment.

BACKGROUND

A hospital computing network can facilitate communication betweenmedical devices, clients, servers, and the like. Medical devices cantransfer treatment related information to healthcare providers over thenetwork. Clients can exchange messages with other clients and push datasets to medical devices over the network. Servers can host applicationsused by clients connected to the network.

As the number of devices connected to the network grows, the number ofmessages that are exchanged across the network can rapidly increase.This increase in message traffic can inundate recipients withnotifications. While some of these notifications can provide importantinformation to a recipient, many of these notifications may beirrelevant or marginally useful.

SUMMARY

In some implementations, methods and apparatus, including computerprogram products, and systems are provided for the distribution ofnotifications to a user based on the user's subscriptions to variousnotification categories.

In one aspect, data encapsulating one or more notifications from adevice is received by at least one data processor via a network. The oneor more notifications provide information relating to a status of thedevice. The device is connected to the network and configured to providea health related treatment for a patient. In addition, each of the oneor more notifications is associated, by at least one data processor,with one or more notification categories. The one or more notificationcategories relate to a function performed by the device or a location ofthe device. A table of one or more users is accessed by at least onedata processor. Each of the one or more users has one or moresubscriptions to the one or more notification categories. The one ormore subscriptions are automatically assigned to the one or more usersbased on a role associated with the one or more users. At least one useris identified, by at least one data processor, from the table todistribute the one or more notifications. The at least one user has atleast one subscription that matches at least one notification categoryof the one or more notifications. Data comprising the one or morenotifications are distributed to the at least one user by at least onedata processor.

The above methods, apparatus, computer program products, and systemscan, in some implementations, further include one or more of thefollowing features.

The distributing can include at least one of loading the one or morenotifications on a notifications page associated with the at least oneuser, sending an e-mail containing the one or more notifications to theat least one user, and sending a text message containing the one or morenotifications to the at least one user. The one or more notificationcategories for the at least one user can be associated by at least onedata processor with at least a high priority and a low priority. Thenotifications page can display notifications in a notification categoryassociated with a high priority before notifications in a notificationcategory associated with a low priority.

The role associated with the one or more users can be based on aposition or a department associated with the one or more users.

The status of the device can indicate whether the device is connected tothe network. The status of the device can specify whether action isrequired from the at least one user.

The device can be selected from a group consisting of an infusion pump,a ventilator, an electrocardiogram, and a computing device hosting adata set editor application. The action required by the notificationsent from the infusion pump can indicate that the infusion pump needs tobe refilled with medication. The action required by the notificationsent from the computing device can indicate that a data set generated bythe data set editor application is awaiting review.

In some implementations, at least one of the subscriptions automaticallyassigned to the at least one user can be automatically deleted by atleast one data processor when the role associated with the at least oneuser changes.

A removal request from the at least one user for at least one of thesubscriptions can be received by at least one data processor. The atleast one subscription can be deleted by at least one data processor.

The one or more notifications can be modified by at least one dataprocessor before the one or more notifications are distributed. Thesemodifications can include the addition of information to the one or morenotifications. This information can include when the one or morenotifications was received.

Computer program products are also described that comprisenon-transitory computer readable media storing instructions, which whenexecuted one or more data processors of one or more computing systems,causes at least one data processor to perform operations herein.Similarly, computer systems are also described that may include one ormore data processors and a memory coupled to the one or more dataprocessors. The memory may temporarily or permanently store instructionsthat cause at least one processor to perform one or more of theoperations described herein. In addition, methods can be implemented byone or more data processors either within a single computing system ordistributed among two or more computing systems. Such computing systemscan be connected and can exchange data and/or commands or otherinstructions or the like via one or more connections, including but notlimited to a connection over a network (e.g. the Internet, a wirelesswide area network, a local area network, a wide area network, a wirednetwork, or the like), via a direct connection between one or more ofthe multiple computing systems, etc.

The subject matter described herein provides many advantages. Forexample, in some implementations, the current subject matter can allownotifications to be distributed to users based on the users'subscriptions to various notification categories. In addition, thecurrent subject matter can allow a user to assign a priority level toeach notification category. The display of these notifications can becustomized based on these priority levels.

The details of one or more variations of the subject matter describedherein are set forth in the accompanying drawings and the descriptionbelow. Other features and advantages of the subject matter describedherein will be apparent from the description and drawings, and from theclaims.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are incorporated herein and constitutea part of this specification, show certain aspects of the subject matterdisclosed herein and, together with the description, help explain someof the principles associated with the subject matter disclosed herein.In the drawings,

FIG. 1 is a system diagram illustrating a computing landscape within ahealthcare environment;

FIG. 2 is a table of notification categories and subscribed users;

FIG. 3 is a notifications page;

FIG. 4A is a priority assignment window;

FIG. 4B is a notifications page that displays notifications based on thepriority associated with various notification categories; and

FIG. 5 is a process flow diagram illustrating distribution ofnotifications to a user based on the user's subscriptions to variousnotification categories.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

The subject matter disclosed herein relates to the distribution ofnotifications to a user based on the user's subscriptions to variousnotification categories. In some implementations, these notificationscan be associated with notification categories that relate to a functionperformed by a device that sent the notification or a location of thedevice that sent the notification.

FIG. 1 is a system diagram illustrating a computing landscape 100 withina healthcare environment such as a hospital. Various devices andsystems, both local to the healthcare environment and remote from thehealthcare environment, can interact via at least one computing network105. This computing network 105 can provide any form or medium ofdigital communication connectivity (i.e., wired or wireless) amongst thevarious devices and systems. Examples of communication networks includea local area network (“LAN”), a wide area network (“WAN”), and theInternet. In some cases, one or more of the various devices and systemscan interact directly via peer-to-peer coupling (either via a hardwiredconnection or via a wireless protocol such as Bluetooth or WiFi). Inaddition, in some variations, one or more of the devices and systemscommunicate via a cellular data network.

In particular, aspects of the computing landscape 100 can be implementedin a computing system that includes a back-end component (e.g., as adata server 110), or that includes a middleware component (e.g., anapplication server 115), or that includes a front-end component (e.g., aclient computer 121 having a graphical user interface or a Web browserthrough which a user may interact with an implementation of the subjectmatter described herein), or any combination of such back-end,middleware, or front-end components. Clients 121, 122, and 123 andservers 110 and 115 are generally remote from each other and typicallyinteract through the communications network 105. The relationship of theclients 121-123 and servers 110 and 115 arises by virtue of computerprograms running on the respective computers and having a client-serverrelationship to each other. Clients 121-123 can be any of a variety ofcomputing platforms that include local applications for providingvarious functionality within the healthcare environment. Example clientsinclude, but are not limited to, desktop computers, laptop computers,tablets, and other computers with touch-screen interfaces. The localapplications can be self-contained in that they do not require networkconnectivity and/or they can interact with one or more of the servers110 and 115 (e.g., a web browser).

A variety of applications can be executed on the various devices andsystems within the computing landscape such as electronic health recordapplications, medical device monitoring, operation, and maintenanceapplications, scheduling applications, data set editor applications,billing applications, and the like.

The network 105 can be coupled to one or more data storage systems 125.The data storage systems 125 can include databases providing physicaldata storage within the healthcare environment or within a dedicatedfacility. In addition, or in the alternative, the data storage systems125 can include cloud-based systems providing remote storage of data in,for example, a multi-tenant computing environment. The data storagesystems 125 can also comprise non-transitory computer readable media.

Mobile communications devices (MCDs) 130 can also form part of thecomputing landscape 100. The MCDs 130 can communicate directly via thenetwork 105 and/or they can communicate with the network 105 via anintermediate network such as a cellular data network 135. Various typesof communication protocols can be used by the MCDs 130 including, forexample, messaging protocols such as SMS and MMS.

Various types of medical devices 140, 141, 142, and 143 can be used aspart of the computing landscape 100. These medical devices 140-143 cancomprise, unless otherwise specified, any type of device or system witha communications interface that characterizes one or more physiologicalmeasurements of a patient and/or that characterize treatment of apatient. In some cases, the medical devices 140-143 communicate via peerto peer wired or wireless communications with another medical device (asopposed to communicating with the network 105). For example, the medicaldevice 140 can comprise a bedside vital signs monitor that is connectedto medical devices 141 and 142, namely a wireless pulse oximeter and toa wired blood pressure monitor. One or more operational parameters ofthe medical devices 140-143 can be locally controlled by a clinician,controlled via a clinician via the network 105, and/or they can becontrolled by one or more of a server 110 and/or 115, clients 121-123,MCDs 130, and/or another medical device.

Application server 115 can run a system event notification applicationthat distributes notifications sent from medical devices 141-143,clients 121-123, MCDs 130, or backend server 110 to various devicesconnected to network 105. These notifications can provide informationrelating to a function provided by a particular device or the status ofthe device. For example, a pharmacist can use one of client computers121-123 to create or modify a data set using a data set editorapplication. This data set can contain device configurations, druglibraries, clinical advisories and other important information formedical devices 140-143. The system event notification application cansend data encapsulating a notification to various care providers tosolicit comments or approval of the data set before the data set isdeployed to medical devices 140-143. In another example, medical devices140-143 can collect data characterizing one or more physiologicalmeasurements of a patient and/or treatment of a patient (e.g., medicaldevices 140-143 can be an infusion management system, etc.). Medicaldevices 140-143 can transmit data encapsulating a notification withthese measurements to application server 115 which, in turn, candistribute data comprising this notification to a particular set ofusers. For example, medical device 140 can correspond to an infusionpump that infuses a patient with medication. As the amount of medicationin the infusion pump depletes below a predetermined threshold, theinfusion pump can send data encapsulating a notification to applicationserver 115 to indicate that a new supply of medication is needed.Application server 115 can then distribute data comprising thisnotification to alert the appropriate personnel.

Before notifications are distributed to users, the system eventnotification application can associate each notification with one ormore notification categories. A notification category can be based ondifferent characteristics associated with the notification including,for example, a function performed by the device that sent thenotification. For example, the system event notification application canautomatically associate messages sent by backend server 110 with aninformation technology (IT) notification category because the backendserver performs IT related functions. If backend server 110, forexample, sends a notification to application server 110 that one of itsstorage devices has failed, then the system event notificationapplication can associate the message with an IT notification categoryand distribute this notification to users having an IT notificationcategory subscription. In another example, the system event notificationapplication can automatically associate notifications received from aventilator or electrocardiogram (ECG) machine (e.g., medical device 140)with a cardiopulmonary notification category because the ventilator andECG machine perform cardiopulomonary functions. As application server115 receives data measurements from either the ventilator or ECGmachine, it can transmit notifications with these measurements to usershaving a cardiopulmonary notification category subscription.

Alternatively or additionally, the notification category can be based ona location of the device that sent the notification. If, for example,the ECG machine described above is used in the intensive care unit of ahospital, the system event notification application can associatemessages sent from the ECG with an intensive care unit notificationcategory. The system event notification application can then transmitnotifications from the ECG in the intensive care unit to users having asubscription to an intensive care unit notification category. Theassociation process can be based on other notification categoriesincluding, for example, a caregiver team (which associates messages froma particular device with a notification category that identifies thecaregivers that monitor the device), configurations settings (whichassociates messages from a device operating outside of preset guardrailswith a notification category that identifies the members of aconfigurations setting group), and the like.

As described above, the system event notification application candistribute data that includes these notifications to users based on theuser's subscriptions to one or more notification categories. Thesesubscriptions can be based on a role performed by the user and can beautomatically assigned to a user based on the user's position within ahospital or a department that the user belongs to. Each role can be acontainer for various permissions associated with the user. Thesepermissions can designate the types of notifications that a user canreceive. The system event notification application can be configured toretrieve position and department information and corresponding userpermissions from an employee database.

For example, a nurse belonging to the emergency room department of ahospital can be automatically subscribed to a nursing staff notificationcategory and an emergency room notification category. If the nurseleaves the emergency room to work in the intensive care unit, the systemevent notification program can automatically update the nurse'ssubscriptions. During this update process, the nurse can beautomatically unsubscribed from the emergency room notification categoryand automatically subscribed to the intensive care unit notificationcategory. In some implementations, the nurse can unsubscribehimself/herself from a notification category by sending a removalrequest to the system event notification application. The system eventnotification application can process the removal request and delete thecorresponding subscription.

FIG. 2 illustrates a table 200 that can be maintained by the systemevent notification application and stored at data storage systems 125.Table 200 can identify different notification categories (in column 205)used by the system event notification application and the userssubscribed to each notification category (in column 210). The systemevent notification application can update table 200 as users aresubscribed and unsubscribed to different notification categories asdescribed above. In addition, the system event notification applicationcan use table 200 to determine which users to send a notification. If,for example, the system event notification application associates areceived notification with an emergency room notification category, theapplication can refer to rows 215 of table 200 to identify the usersthat have a subscription to this notification category (i.e., user 1,user 3, and user 4) and distribute the notification to these subscribedusers. As illustrated in table 200, some users can have multiplesubscriptions. For example, as indicated by rows 220, user 4 can receivenotifications associated with emergency room, intensive care unit, anddata set review notification categories.

Once the system event notification application has identified whichusers should receive a particular notification, it can distribute datathat includes the notification to these users. The system eventnotification application can distribute these notifications in theiroriginal form or modify them to include less information or additionalinformation. The additional information can include, for example, thedate/time that the application server received the notification from thedevice, and the like. Distribution can occur via different modalities.For example, the system event notification application can send dataincluding the notification to an address associated with the user (e.g.,an e-mail address or a text message phone number). In someimplementations, these notifications can be displayed on a user'snotifications page 300 as illustrated in FIG. 3. A user can accesshis/her notification page by logging onto the system event notificationapplication using, for example, computer clients 121-123 or MCDs 130.

Notifications page 300 can display all of the notifications for user 4from table 200. For each of these notifications, notifications page 300can display the notification category (in column 305), a statusassociated with the notification (in column 310), and the date/time thatthe notification was distributed from application server 115 (in column315). In some implementations, column 315 can also display the date/timethat application server 115 received the notification from theoriginating device. As explained above with respect to FIG. 2, user 4can have subscriptions to emergency room, intensive care unit, and dataset review notification categories, and these notifications can bedisplayed at rows 320, 325, and 330, respectively.

The status description (in column 310) can provide information regardingthe device that sent the notification. This information can include, forexample, whether the device is connected to network 105, when the deviceis turned on, when the device is turned off, and the like. The statusdescription (in column 310) can also indicate whether a notificationrequires user action. For example, the status associated withnotification 320 can indicate that infusion pump A in the emergency roomneeds to be refilled with medication. This notification can appear onthe notifications page of all users that have an emergency roomnotification category subscription. Once infusion pump A has beenrefilled, the pump can report its status to application server 115. Uponreceiving this status message, the system event notification applicationcan delete the original notification from the notification page of thedesignated subscribers and/or send a follow-up notification to thesubscribers to indicate that action is no longer required. In anotherexample, the status associated with notification 330 can indicate thatdata set C is awaiting review by user 4. This notification can appearwhen an entity designates user 4 as a reviewer for data set C and canremain on notifications page 300 until user 4 completes the review.

A user can customize his/her notifications page by groupingnotifications according to their priority levels. This feature can beuseful, for example, when a user has subscriptions to numerousnotification categories and wants to review notifications from the mostimportant categories first. The user can designate the relativeimportance of different notification categories by assigning a prioritylevel to each category. A user can, for example, use window 400 of FIG.4A to assign a high priority level 405 or a low priority level 410 to anotification category. Window 400 can appear when a user, for example,clicks on or hovers over a notification category 305 on notificationspage 300. In the example of FIG. 3, user 4 can use window 400 to assigna high priority level to the intensive care unit notification categoryand a low priority level to the emergency room and data set reviewnotification categories. Although the implementation of FIG. 4Aillustrates two priority levels (i.e., low and high), any number ofpriority levels can be used (e.g., low, medium, high, and urgent).

As a user assigns priority levels to each notification category, thesystem event notification program can modify the appearance ofnotifications page 300. Based on the priority levels assigned by user 4,notifications window 450 in FIG. 4B can display notifications in a highpriority notification category (i.e., intensive care unit) beforenotifications in a low priority notification category (i.e., emergencyroom and data set review).

FIG. 5 illustrates a flowchart 500 for distributing notifications to auser based on the user's subscriptions to various notificationcategories. At 505, application server 115 can receive via a networkdata encapsulating a notification from a device connected to thenetwork. The device can be configured to provide a health relatedtreatment for a patient and can be, for example, any one of medicaldevices 140-143, clients 121-123, MCDs 130, or backend server 110. Insome implementations, the device can be a computing device that hosts adata set editor application that generates data sets to be used bymedical devices 140-143. The data encapsulating the notification sent bythe device can provide information relating to the status of the device.

At 510, the system event notification application running on applicationserver 115 can associate the notification received at 510 with one ormore notification categories. Notification categories can be associatedwith a function performed by the device that sent the notification. Insome implementations, notification categories can be associated with alocation of the device that sent the notification.

At 515, the system event notification application can access a table ofnotification categories and subscribed users. This table can be storedat data storage systems 125 and can identify which users are subscribedto a particular notification category. The system event notificationapplication can automatically assign subscriptions to users based on oneor more roles associated with the user. Each of these roles can beassociated with various permissions that designate the type ofnotifications that a user can receive. This role can be based on, forexample, the user's position or a department that the user is a memberof.

At 520, the system event notification application can identify whichusers to distribute the notification to. A user can be eligible toreceive a notification if he/she has a subscription to the notificationcategory associated with the notification received at 505. The systemevent notification application can determine whether there is anotification category—user subscription match by referring to the tableaccessed at 515. If there is a match, then the system event notificationapplication can distribute the notification to the user.

At 525, the system event notification application can distribute datacomprising the notification to the users identified at 520. In someimplementations, the notification can be loaded onto a notificationspage associated with the user or sent to an address associated with theuser (e.g., an e-mail address or a text message phone number). In someimplementations, the user can assign a priority level to eachnotification category, and the notifications page can displaynotifications in accordance with these assigned priority levels.

One or more aspects or features of the subject matter described hereincan be realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device (e.g., mouse, touch screen, etc.), andat least one output device.

These computer programs, which can also be referred to programs,software, software applications, applications, components, or code,include machine instructions for a programmable processor, and can beimplemented in a high-level procedural language, an object-orientedprogramming language, a functional programming language, a logicalprogramming language, and/or in assembly/machine language. As usedherein, the term “machine-readable medium” refers to any computerprogram product, apparatus and/or device, such as for example magneticdiscs, optical disks, memory, and Programmable Logic Devices (PLDs),used to provide machine instructions and/or data to a programmableprocessor, including a machine-readable medium that receives machineinstructions as a machine-readable signal. The term “machine-readablesignal” refers to any signal used to provide machine instructions and/ordata to a programmable processor. The machine-readable medium can storesuch machine instructions non-transitorily, such as for example as woulda non-transient solid state memory or a magnetic hard drive or anyequivalent storage medium. The machine-readable medium can alternativelyor additionally store such machine instructions in a transient manner,such as for example as would a processor cache or other random accessmemory associated with one or more physical processor cores.

To provide for interaction with a user, the subject matter describedherein can be implemented on a computer having a display device, such asfor example a cathode ray tube (CRT) or a liquid crystal display (LCD)monitor for displaying information to the user and a keyboard and apointing device, such as for example a mouse or a trackball, by whichthe user may provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well. For example,feedback provided to the user can be any form of sensory feedback, suchas for example visual feedback, auditory feedback, or tactile feedback;and input from the user may be received in any form, including, but notlimited to, acoustic, speech, or tactile input. Other possible inputdevices include, but are not limited to, touch screens or othertouch-sensitive devices such as single or multi-point resistive orcapacitive trackpads, voice recognition hardware and software, opticalscanners, optical pointers, digital image capture devices and associatedinterpretation software, and the like.

The subject matter described herein can be embodied in systems,apparatus, methods, and/or articles depending on the desiredconfiguration. The implementations set forth in the foregoingdescription do not represent all implementations consistent with thesubject matter described herein. Instead, they are merely some examplesconsistent with aspects related to the described subject matter.Although a few variations have been described in detail above, othermodifications or additions are possible. In particular, further featuresand/or variations can be provided in addition to those set forth herein.For example, the implementations described above can be directed tovarious combinations and subcombinations of the disclosed featuresand/or combinations and subcombinations of several further featuresdisclosed above. In addition, the logic flow(s) depicted in theaccompanying figures and/or described herein do not necessarily requirethe particular order shown, or sequential order, to achieve desirableresults. Other implementations may be within the scope of the followingclaims.

What is claimed is:
 1. A method comprising: receiving, by at least oneprocessor via a network, data encapsulating a first notificationincluding a physiological measurement of a patient and a status of aninfusion pump associated with the patient, the status of the infusionpump specifying an action to be performed at the infusion pump;associating, by the at least one processor, the first notification witha first notification category, the association based on characteristicsassociated with the first notification, the first notification categoryrelating to the action to be performed by the infusion pump andassociated with a location of the infusion pump; assigning, by the atleast one processor, one or more users including a first user to a firstsubscription associated with the first notification category, whereinthe assignment is based at least in part on (i) a plurality of rolesincluding a first role and a second role associated with the one or moreusers and (ii) locations of the one or more users, wherein assignmentinformation for the one or more users is accessible to the at least oneprocessor; identifying, by the at least one processor, the first userfrom the table of users for distribution of the first notification, thefirst user assigned to the first subscription matching the firstnotification category; and clearing, by the at least one processor, thefirst notification in response to detection that the action to beperformed at the infusion pump is completed.
 2. The method of claim 1,wherein the first notification is populated on a notification page inresponse to identifying the first user from the table of users fordistribution of the first notification.
 3. The method of claim 2,wherein the first notification is cleared from the notification page inresponse to detection by the at least one processor that the action tobe performed at the infusion pump is completed.
 4. The method of claim1, wherein the detection that the action to be performed at the infusionpump is completed is based on a status sent by the infusion pump to theat least one processor.
 5. The method of claim 1, further comprising:distributing, by the at least one processor, a follow-up notification tothe one or more users including the first user, the follow-upnotification indicating that the action to be performed at the infusionpump is completed.
 6. The method of claim 1, wherein the dataencapsulating the first notification is sent to the at least oneprocessor from a medical device that collects the physiologicalmeasurement of the patient and that is in communication with theinfusion pump.
 7. The method of claim 1, further comprising:identifying, by the at least one processor, one or more other users notincluding the first user from the table of users for distribution of thefirst notification, the one or more other uses assigned to the firstsubscription matching the first notification category; and distributing,by the at least one processor, data comprising the first notificationincluding the physiological measurement of the patient to the one ormore other users.
 8. A non-transitory computer-readable mediumcontaining instructions to configure at least one processor to performoperations comprising: receiving, by the at least one processor via anetwork, data encapsulating a first notification including aphysiological measurement of a patient and a status of an infusion pumpassociated with the patient, the status of the infusion pump specifyingan action to be performed at the infusion pump; associating, by the atleast one processor, the first notification with a first notificationcategory, the association based on characteristics associated with thefirst notification, the first notification category relating to theaction to be performed by the infusion pump and associated with alocation of the infusion pump; assigning, by the at least one processor,one or more users including a first user to a first subscriptionassociated with the first notification category, wherein the assignmentis based at least in part on (i) a plurality of roles including a firstrole and a second role associated with the one or more users and (ii)locations of the one or more users, wherein assignment information forthe one or more users is accessible to the at least one processor;identifying, by the at least one processor, the first user from thetable of users for distribution of the first notification, the firstuser assigned to the first subscription matching the first notificationcategory; and clearing, by the at least one processor, the firstnotification in response to detection that the action to be performed atthe infusion pump is completed.
 9. The non-transitory computer-readablemedium of claim 8, wherein the first notification is populated on anotification page in response to identifying the first user from thetable of users for distribution of the first notification.
 10. Thenon-transitory computer-readable medium of claim 9, wherein the firstnotification is cleared from the notification page in response todetection by the at least one processor that the action to be performedat the infusion pump is completed.
 11. The non-transitorycomputer-readable medium of claim 8, wherein the detection that theaction to be performed at the infusion pump is completed is based on astatus sent by the infusion pump to the at least one processor.
 12. Thenon-transitory computer-readable medium of claim 8, the operationsfurther comprising: distributing, by the at least one processor, afollow-up notification to the one or more users including the firstuser, the follow-up notification indicating that the action to beperformed at the infusion pump is completed.
 13. The non-transitorycomputer-readable medium of claim 8, wherein the data encapsulating thefirst notification is sent to the at least one processor from a medicaldevice that collects the physiological measurement of the patient andthat is in communication with the infusion pump.
 14. The non-transitorycomputer-readable medium of claim 8, the operations further comprising:identifying, by the at least one processor, one or more other users notincluding the first user from the table of users for distribution of thefirst notification, the one or more other uses assigned to the firstsubscription matching the first notification category; and distributing,by the at least one processor, data comprising the first notificationincluding the physiological measurement of the patient to the one ormore other users.
 15. A system comprising: at least one processor; and amemory, wherein the at least one processor and the memory are configuredto perform operations comprising: receiving, by the at least oneprocessor via a network, data encapsulating a first notificationincluding a physiological measurement of a patient and a status of aninfusion pump associated with the patient, the status of the infusionpump specifying an action to be performed at the infusion pump;associating, by the at least one processor, the first notification witha first notification category, the association based on characteristicsassociated with the first notification, the first notification categoryrelating to the action to be performed by the infusion pump andassociated with a location of the infusion pump; assigning, by the atleast one processor, one or more users including a first user to a firstsubscription associated with the first notification category, whereinthe assignment is based at least in part on (i) a plurality of rolesincluding a first role and a second role associated with the one or moreusers and (ii) locations of the one or more users, wherein assignmentinformation for the one or more users is accessible to the at least oneprocessor; identifying, by the at least one processor, the first userfrom the table of users for distribution of the first notification, thefirst user assigned to the first subscription matching the firstnotification category; and clearing, by the at least one processor, thefirst notification in response to detection that the action to beperformed at the infusion pump is completed.
 16. The system of claim 15,wherein the first notification is populated on a notification page inresponse to identifying the first user from the table of users fordistribution of the first notification.
 17. The system of claim 16,wherein the first notification is cleared from the notification page inresponse to detection by the at least one processor that the action tobe performed at the infusion pump is completed.
 18. The system of claim15, wherein the detection that the action to be performed at theinfusion pump is completed is based on a status sent by the infusionpump to the at least one processor.
 19. The system of claim 15, theoperations further comprising: distributing, by the at least oneprocessor, a follow-up notification to the one or more users includingthe first user, the follow-up notification indicating that the action tobe performed at the infusion pump is completed.
 20. The system of claim15, wherein the data encapsulating the first notification is sent to theat least one processor from a medical device that collects thephysiological measurement of the patient and that is in communicationwith the infusion pump.